This example explains how to use the \path{xmdefconfig} file. If you
require a more complex setup, you will want to write a custom
configuration file --- details of the configuration file formats are
-included in Chapter~\ref{cha:config}.
+included in Section~\ref{s:cfiles}.
The \path{xmexample1} file is a simple template configuration file
for describing a single VM.
fills in parts of this template.
Both of them can be found in \path{/etc/xen/}
-\subsection{Editing \path{xmdefconfig}}
+\section{Editing \path{xmdefconfig}}
-At minimum, you should edit the following variables in \path{/etc/xen/xmdefconfig}:
+At minimum, you should edit the following
+variables in \path{/etc/xen/xmdefconfig}:
\begin{description}
\item[kernel] Set this to the path of the kernel you compiled for use
If you don't have a \path{xmdefconfig} file, simply create your own
by copying one of the \path{/etc/xen/xmexample} files.
-\subsection{Starting the domain}
+\section{Starting the domain}
The {\tt xm} tool provides a variety of commands for managing domains.
Use the {\tt create} command to start new domains. To start the
using the xm tool (see Section~\ref{s:xm}) and the experimental
Xensv web interface (see Section~\ref{s:xensv}).
-\section{The xm tool}
+\section{Xm (Command line interface)}
\label{s:xm}
The xm tool is the primary tool for managing Xen from the console.
%\part{Advanced Topics}
-\chapter{Network Configuration}
+\section{Network Configuration}
For simple systems with a single ethernet interface with a simple
configuration, the default installation should work `out of the
The purpose of this chapter is to describe the mechanisms provided by
\xend to allow a flexible configuration for Xen's virtual networking.
-\section{Xen networking scripts}
+\subsection{Xen networking scripts}
Xen's virtual networking is configured by 3 shell scripts. These are
called automatically by \xend when certain events occur, with arguments
scripts are found by default in \path{/etc/xen}. The names and
locations of the scripts can be configured in \path{xend-config.sxp}.
-\subsection{\path{network}}
+\subsubsection{\path{network}}
This script is called once when \xend is started and once when \xend is
stopped. Its job is to do any advance preparation required for the
which causes it to delete the Xen bridge and remove {\tt eth0} from
it, restoring the normal IP and routing configuration.
-\subsection{\path{vif-bridge}}
+\subsubsection{\path{vif-bridge}}
This script is called for every domain virtual interface. This should
do things like configuring firewalling rules for that interface and
This script can be customized to properly deal with more complicated
bridging setups.
-\chapter{Scheduler Configuration}
+\section{Scheduler Configuration}
-\section{Scheduler selection}
+\subsection{Scheduler selection}
Xen offers a boot time choice between multiple schedulers. To select
a scheduler, pass the boot parameter { \tt sched=sched\_name } to Xen,
scheduler is the recommended choice, since the Atropos scheduler is
not finished.
-\section{Borrowed Virtual Time}
+\subsection{Borrowed Virtual Time}
{\tt sched=bvt } (the default) \\
observed to penalise domains that block frequently (e.g. IO intensive
domains), but this can be compensated by using warping.
-\subsection{Global Parameters}
+\subsubsection{Global Parameters}
\begin{description}
\item[ctx\_allow]
pre-empted. This prevents thrashing of the CPU.
\end{description}
-\subsection{Per-domain parameters}
+\subsubsection{Per-domain parameters}
\begin{description}
\item[mcuadv]
run unwarped for before it can warp again
\end{description}
-\section{Atropos}
+\subsection{Atropos}
{\tt sched=atropos } \\
more CPU than is available - the utilisation should be kept to
slightly less than 100% in order to ensure predictable behaviour).
-\subsection{Per-domain parameters}
+\subsubsection{Per-domain parameters}
\begin{description}
\item[slice]